Skip to content

fix: Runtime does not start workers for tools declared on a planner= agent - #529

Closed
nandanadileep wants to merge 1 commit into
conductor-oss:mainfrom
nandanadileep:oss-harness/issue-478
Closed

nandanadileep wants to merge 1 commit into
conductor-oss:mainfrom
nandanadileep:oss-harness/issue-478

Conversation

@nandanadileep

Copy link
Copy Markdown

Fixes #478.

Focused Python fix for: Runtime does not start workers for tools declared on a planner= agent

Changed implementation: src/conductor/ai/agents/runtime/runtime.py.
Regression tests: tests/unit/ai/test_plan_execute_worker_traversal.py.

Verification (working directory .): .venv/bin/python -m pytest -q -x -p no:cacheprovider -- /workspace/tests/unit/ai/test_plan_execute_worker_traversal.py

  • Patched code: 8 tests, zero failures/errors.
  • Original code with the same regression tests: 1 failures, zero collection/setup errors.
  • Base commit: 729c1ce8ffb0a1d527caa652a25abdff181f5dba.

AI-assisted contribution: OpenCode using Autoloops wrote this patch. The automated harness independently ran the tests listed above. No human review is claimed.

@nandanadileep

Copy link
Copy Markdown
Author

Closing as part of cleaning up automated contribution volume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Runtime does not start workers for tools declared on a planner= agent

1 participant